home *** CD-ROM | disk | FTP | other *** search
- Path: anvil.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: malloc()
- Date: 28 Feb 1996 11:41:14 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4h2b4qINNdh0@anvil.ugrad.cs.ubc.ca>
- References: <31346F12.167E@mashie.ece.jhu.edu>
- NNTP-Posting-Host: anvil.ugrad.cs.ubc.ca
-
- In article <31346F12.167E@mashie.ece.jhu.edu>,
- Chenyang Xu <chenyang@mashie.ece.jhu.edu> wrote:
- >Hi, there,
- >
- > I posted a question about debugging problems related to malloc().
- >Thanks for a wonderful comp.lang.c newsgroup. The replys are very
- >helpful. With these help, I am able to detect the bug in my program
- >which has been bugging for several days. As an appreciation, I compiled
- >the replies I got and post them back and hope other people can benefit
- >from these replies.
- >
- > Before I go on, I'd like to advocate the use of ElectricFence to
- >debug problems related to malloc(), calloc(), and free() etc. I got this
-
- me too.
-
- >advice from c2a192@ugrad.cs.ubc.ca. I compiled it and it helped me find
- >the bug quickly together with some knowledges I learned from other
-
- It's awesome. When in doubt, use hardware! The associative TLB lookup hardware
- that your CPU uses to do virtual address translation is far faster at catching
- bad pointers than any emulator/bounds checker. :)
- --
-
-